Added the feature discussed in the issue #144, the goal is to be able to publish outdated-browser on npmjs without affecting current way of doing things

Gulp for compilation

To minify and jshint file I created a gulp configuration with two tasks

• default to minify js / css
• server to serve the demo (localhost:3001/demo) and watch files (editing the js will minify it)

File structure

The goal is to make the directory easier to understand putting all the files needed in a dist directory.

├── demo/
│   └── index.html
├── dist/
│   └── outdatedbrowser.js
│   └── outdatedbrowser.css
│   └── lang/
├── src/
│   └── outdatedbrowser.js
│   └── outdatedbrowser.css

If you don't like this idea, you can tell me and I'll revert back to what it was

Added a new "force" option

I noticed in your demo that you had no way to force outdatedbrowser.js so I added a new option to force it. It can be usefull if some people willing to check custom with additional librairies (modernizr for instance)

In my opinion it could be interesting to add a new option to create a custom support method (just an idea)

Added module loader support

This was the main goal of this PR, I used umd (Universal Module Definition) to make outdatedbrowser loadable with requirejs or browserify.

I didn't published the plugin on npm cause you are the author (and maybe you want to keep the control), but I can do it if you want if this code is merged with master)

Sorry for my English :(